Tuner Test

The Tuner Test procedure:

  • Sets the tuning stubs according to the active Scenario, and for each setting

  • retrieves the measurement results,

  • stores the results to an output text file.

  • Repeats the whole cyclus indefinitely until

  • the user stops it, or

  • an excessive number of consecutive motor errors occurs.

The output file is created and named automatically. The file name includes the date and time of its creation, having the form TunerTest_yymmdd_hhmmss.txt. The file is written to the User Folder. The file structure is as described in Scenario Output Files.

The test should be performed without microwave power. This is partly because only behavior of tuning stubs/stepper motors is of interest. Another reason is that deep stubs insertions could cause problems when microwave power is applied. A typical returned Homer Error Byte is, therefore, 48 = 16 (Low Signal) + 32 (Substitute Frequency).

To start Tuner Test, proceed as follows:

  • In the context menu (right-click the scenario table to open it), click Autofill to generate a scenario.

  • Alternatively, you can create a scenario using the Fill Random menu item or by any other method discussed here.

  • In the context menu, click Run Tuner Test and follow the prompts.

  • Without motor errors, the test continues indefinitely.

  • To stop the Tuner Test immediately, click the top left Play/Stop button .

  • Alternatively, to first continue until the Scenario end, and then stop the Tuner Test, click the Cyclic button sbFreeRun to deactivate it.

  • When the test is stopped, the program will inform you about the created file and prompt you to open the User Folder.

Handling Motor Errors

The main purpose of the Tuner Test is to run long-lasting comprehensive tests with moving stubs, detecting and recording potential faults of the stepper motors or tuning stubs. In order for the test not to be stopped immediately after an error occurs, the motor errors (based on the value of Motor Status Byte MS2) are handled as follows:

  • The remark MotxyzErr! is added at the end of the corresponding output file row where x, y, z stand for the numbers of the motors in error. If, for instance motors 1 and 3 are in error, the remark reads Mot13Err!. The remark is separated by a tab character (ASCII #9).

  • An All Stubs Home procedure is attempted.

  • If the attempt was successful, the Tuner Test proceeds.

  • If the attempt failed, another All Home attempt is made.

  • If the number of successive failed attempts exceeds a defined limit (typically 10), this is an indication of a fatal error. In this case, the Tuner Test is aborted.

  • If a successful All Home attempt occurs before reaching this limit, the fail count is restored to zero and the Tuner Test continues.